Columbia U./Cisco Systems RTP Profile for Audio and Video Conferences with Minimal Control

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress". Abstract This memorandum is a revision of RFC 1890 in preparation for advancement from Proposed Standard to Draft Standard status. Readers are encouraged to use the PostScript form of this draft to see where changes from RFC 1890 are marked by change bars. This document describes a profile called "RTP/AVP" for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings. This document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names Schulzrinne/Casner [Page 1] Internet Draft Profile January 14, 2000 when used within RTP. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications. Resolution of Open Issues [Note to the RFC Editor: This section is to be deleted when this draft is published as an RFC but is shown here for reference during the Last Call. The first paragraph of the Abstract is also to be deleted. All RFC XXXX should be filled in with the number of the RTP specification RFC submitted for Draft Standard status, and all RFC YYYY should be filled in with the number of the draft specifying MIME registration of RTP payload types as it is submitted for Proposed Standard status. These latter references are intended to be non-normative.] Readers are directed to Appendix 9, Changes from RFC 1890, for a listing of the changes that have been made in this draft. The changes from RFC 1890 are marked with change bars in the PostScript form of this draft. The revisions in this draft are intended to be complete for Last Call. The following …